|
1. Defining the test basis
| The test basis, or the gathering of all the written and unwritten requirements with which the test object should comply,
can take various forms. Bear in mind, for example, requirements, acceptance criteria, functional designs, technical
designs, user manuals, interviews, reports of meetings, legislation, but not forgetting the old system, a previous release
of the system, a prototype or even a domain expert. The gathering of non-documented test basis in particular is difficult.
It is important when determining the test basis to ensure that the non-functional requirements are also known, such as e.g.
requirements in respect of performance or security. Something to be kept in mind in respect of the test basis is that these
requirements should be as concrete and measurable (testable) as possible to prevent misunderstandings. This is often not
the case in practice. Where possible, it can already be observed at this stage, otherwise it will become apparent at the
later stages of Preparation and Specification. It is also possible that, at a later stage, it will be discovered that a
requirement is very difficult to test. In such cases, it is agreed with the client whether a simplified test is acceptable. |
2. Identifying the test basis
| Establish, as far as possible, the identification of the relevant test basis. Bear in mind the delivery date, version,
status, etc. |
|
